Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

src/components/ClinicalDashboard.tsx (1)

2573-2589: 🩺 Stability & Availability | 🔵 Trivial | ⚡ Quick win

Use authBoundFetch instead of plain fetch for consistency and cancellation.

Every other mutation in this file (mutateDocumentLabel, retryJob, reindexDocument) goes through authBoundFetch, which ties the request to an AbortController and validates the auth epoch before committing state. This call uses plain fetch with no abort signal, so a hung request leaves pendingFeedback set indefinitely (buttons stuck disabled) with no way to cancel on unmount or a superseding auth event.

♻️ Proposed fix

-      const response = await fetch("/api/answer-feedback", {
-        method: "POST",
-        headers: {
-          "Content-Type": "application/json",
-          ...authorizationHeader,
-        },
-        body: JSON.stringify({
-          interactionId: answer.interactionId,
-          feedbackCategory: feedbackType,
-          answerHash,
-          sourceIds: sourceChunkIds,
-          citedSourceIds: citedChunkIds,
-          route: answer.routingMode ?? null,
-          model: answer.modelUsed ?? null,
-          providerRequestIds: answer.openAIRequestIds ?? [],
-        }),
-      });
+      const { response, requestEpoch } = await authBoundFetch("/api/answer-feedback", {
+        method: "POST",
+        headers: {
+          "Content-Type": "application/json",
+          ...authorizationHeader,
+        },
+        body: JSON.stringify({
+          interactionId: answer.interactionId,
+          feedbackCategory: feedbackType,
+          answerHash,
+          sourceIds: sourceChunkIds,
+          citedSourceIds: citedChunkIds,
+          route: answer.routingMode ?? null,
+          model: answer.modelUsed ?? null,
+          providerRequestIds: answer.openAIRequestIds ?? [],
+        }),
+      });
+      if (!isAuthEpochCurrent(requestEpoch)) return;

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/ClinicalDashboard.tsx` around lines 2573 - 2589, Replace the
plain fetch call in the answer-feedback mutation with the file’s existing
authBoundFetch helper, passing the same POST options and request body while
preserving the authorization headers. Ensure the mutation uses the helper’s
cancellation and auth-epoch behavior so pendingFeedback can be cleared when the
request is aborted or superseded.

tests/answer-feedback-route.test.ts (1)

11-56: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Consider covering the duplicate/rate-limited/demo-mode branches too.

Only the happy path is tested. The 409 duplicate-detection branch, 429 rate-limited branch, and demo-mode 400 rejection in route.ts are untested, and the duplicate branch is exactly what's flagged as fragile in src/app/api/answer-feedback/route.ts.

As per path instructions, "For high-risk code involving authentication, authorization, private data, database access, clinical output, ingestion, provider calls, billing, uploads, or background jobs, review carefully for regressions, missing tests, rollback safety, and conservative failure behavior."

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@tests/answer-feedback-route.test.ts` around lines 11 - 56, Expand the “answer
feedback route” tests to cover the 409 duplicate-detection, 429 rate-limit, and
400 demo-mode rejection branches in POST. Reconfigure the existing mocks to
trigger each branch, assert the corresponding response status, and verify
duplicate handling remains covered as implemented in route.ts.

Source: Path instructions

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes